Dynomotion

Group: DynoMotion Message: 8494 From: ericncn Date: 10/18/2013
Subject: logic of the zero/set buttons (bug?)
Hello,

it looks me there's a bug in the logic of the zero/set buttons in KmotionCNC but as nobody else complained till now, maybe it's just me doing something wrong?

Let me explain.

Let's say I am in G55 and need to "zero" my tool relative to a workpiece. I carefully move the axes until the endmill is in the intended position, click on "zero" (or maybe "set" a value, typically half the diameter the probe used) and from now on the GCode I've written for that workpiece is valid.  OK.

Then I move to another fixture offset, let's say I do a G56, and repeat the procedure for the workpiece held in fixture G56.
When I click on "zero"..... it changes the global offset!!!
Which also affects the workpiece in G55 !!

From now on, the GCode for the piece in G56 is valid but the GCode for the piece in G55 is not valid anymore!!
Why that?

I personally would expect that "zeroing" would only affect the currently selected fixture offset and the others would stay unchanged.

Global offset, as it affects all the fixture offsets, should only be changed if explicitly asked!

Am I doing anything wrong?
What's the intended way to define different fixture offsets?

Thank you
EC
Group: DynoMotion Message: 8495 From: Tom Kerekes Date: 10/18/2013
Subject: Re: logic of the zero/set buttons (bug?)
Hi EC,

That isn't a bug.  The Zero/Set buttons change the G92 offset by design.  Sounds like changing fixture offsets might make more sense but not everyone might agree.  Maybe that needs to be an option.

There is now a "set" button near the fixture offset selector, but that "sets" fixture offsets for all axes to make the DROs read.

You can make custom buttons to do this if you wish.  This was discussed in this thread:

http://groups.yahoo.com/neo/groups/DynoMotion/conversations/topics/8230

Using a custom Button/C Program can also allow you to handle things like an automatic probe, or automatically including a probe offset.

See

C:\KMotion431k\C Programs\ToolTableSet.c
C:\KMotion431k\C Programs\SetFixtureX.c
C:\KMotion431k\C Programs\SetFixtureY.c

Regards
TK


Group: DynoMotion Message: 8507 From: ericncn Date: 10/22/2013
Subject: Re: logic of the zero/set buttons (bug?)
Hi Tom,

I've joined that discussion. Those SetFixtureX.c/SetFixtureY.c/ToolTableSet.c + the file SetFixtureZ.c do exactly what I needed, thank you.

But, let me question this... this is a basic functionality that should be included in KmotionCNC by default, and is now consumimg me 4 user buttons (out of 10 available, that's a waste) while the existing zero/set buttons (6 buttons total) sit there unused.

How many people did actually ask, or is relying, on the fact the existing buttons are changing the G92 offset?

Please note that people using only one fixture offset in same program wouldn't notice any difference (regadless you change G92 or the current offset, algebric sum is the same)

This matter would only affect people using multiple fixture offsets in same program but then I wonder who would expect that when you set one fixture offset, all the other offsets get messed up?
Really, if anybody in this newsgroup is relying on this feature, please tell it now!

And, if the existing zero/set buttons would change the currently selected offset, you could still change the G92 if needed, symply by selecting G92 as the current offset (so no functionality would be lost).

Regards
EC

---In DynoMotion@yahoogroups.com, <dynomotion@yahoogroups.com> wrote:

Hi EC,

That isn't a bug.  The Zero/Set buttons change the G92 offset by design.  Sounds like changing fixture offsets might make more sense but not everyone might agree.  Maybe that needs to be an option.

There is now a "set" button near the fixture offset selector, but that "sets" fixture offsets for all axes to make the DROs read.

You can make custom buttons to do this if you wish.  This was discussed in this thread:

http://groups.yahoo.com/neo/groups/DynoMotion/conversations/topics/8230

Using a custom Button/C Program can also allow you to handle things like an automatic probe, or automatically including a probe offset.

See

C:\KMotion431k\C Programs\ToolTableSet.c
C:\KMotion431k\C Programs\SetFixtureX.c
C:\KMotion431k\C Programs\SetFixtureY.c

Regards
TK